fix: add missing Continue support to release workflow and agent scripts#943
fix: add missing Continue support to release workflow and agent scripts#943rohitsoni007 wants to merge 9 commits intogithub:mainfrom
Conversation
|
Quick note: I reviewed the SpecKit README and CLI docs while preparing an internal reference for Spec-Driven Development in another project. The README's |
|
also added commit to same pull request further fix and enhance to turn automatically detected in continue chat window when pressing / name: speckit.analyze only for continnue agent |
| body=$(printf '%s\n' "$body" | sed "s/{ARGS}/$arg_format/g" | sed "s/__AGENT__/$agent/g" | rewrite_paths) | ||
|
|
||
| # If agent is 'continue', prepend special YAML header | ||
| if [[ $agent == "continue" ]]; then |
There was a problem hiding this comment.
I feel like this function needs to be more generic, that is - have a separate function for insertion of custom YAML frontmatter into prompt files, and then invoke it with the argument of invokable and a value of true.
There was a problem hiding this comment.
I've refactored the code to extract the YAML frontmatter insertion logic into a separate, more generic function called insert_yaml_frontmatter. This function can now be reused for other field insertions in the future.
The new function takes four parameters:
body: The content to processname: The name to use for thespeckit.{name}entryfield_name: The field name to insert (e.g., "invokable")field_value: The value for that field (e.g., "true")
This approach makes the code more maintainable and follows the DRY principle. When the agent is "continue" and a description is present, it still inserts the name: speckit.{name} and invokable: true fields into the YAML frontmatter of the prompt files, but now does so by calling the generic function with the appropriate parameters.
This also makes it easier to add other custom fields in the future without duplicating the AWK logic.
|
@rohitsoni-dev if you would like some assistance, please let me know. I'm an avid Continue user and was going to get to this eventually, but am glad to see someone else has taken the initiative. |
|
@maxxrdrgz Appreciate your offer to help! I've actually just finished implementing to add support for continue. |
|
Would love to see this get merged. I'm a contributor to the continue project. |
|
I am a heavy user of Continue and look forward to the integration. |
|
updated: 15 nov, 2025 |
|
Hello, while testing this branch, I cannot have the shell scripts to be executed by the AI, thus the git branch is not created and the templates are not copied. Using Qwen3-30B-A3B as model. |
|
May I inquire about the current progress status? We have been closely monitoring developments and look forward to the early implementation of the specification in continue. |
|
hello admin, please check the pull request and kindly merge the pr, as i am a regular user of continue, i want to use it with speckit |
7 participants
🧩 Related Issue
Fixes #942
📝 Description
Added: add continue support for Spec kit
This pull request addresses the issue mentioned in #942 by implementing the following changes:
✅ Changes Summary
.github/workflows/scripts/create-release-packages.sh
README.md
scripts/bash/update-agent-context.sh
scripts/powershell/update-agent-context.ps1
src/specify_cli/init.py
.github/workflows/scripts/create-github-release.sh
updated: 19 oct
update for auto adding /command in continue
updated: 15 nov
conflict resolved
working example after build release:-
